Power-optimized image capture and push

ABSTRACT

An example security sensor includes a battery power supply, camera coupled to the battery power supply to receive power, activity sensor, processor, and microcontroller. The processor is placed in a sleep state and is wakeable to an awake state. The processor coupled to the battery power supply, and coupled to the camera to receive and process image data including images of an activity within a zone. The microcontroller is coupled to the battery power supply, coupled to the activity sensor to receive interrupts responsive to detection by the activity sensor of the activity within the zone proximate the security sensor, coupled to the processor to send and receive data, and, responsive to receiving a first interrupt from the activity sensor, place the processor in an awake state to signal the camera to capture a set of images and to receive and process the image data including the set of images.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. § 119(e) of U.S.Provisional Patent Application No. 62/077,836, entitled “PremisesMonitoring and Threat Detection, Reporting, and Mitigation” and filedNov. 10, 2014, the entire contents of which are incorporated herein byreference.

BACKGROUND

The present disclosure relates to power management for security sensors.

Existing security system providers provide home and business owners withsecurity systems to monitor their homes and establishments for variousthreats, such as intruders, fires, etc. However, these providersgenerally use large call centers staffed by personnel who are taskedwith calling stakeholders when their security systems have been trippedby security threat, such as an intruder breaking into a home. These callcenters are expensive to operate and the costs for operating them arepassed along to the providers' customers. More particularly, customersare generally required to sign contracts and pay relative expensivemonthly subscription fees in order to access the security servicesprovided by these solutions. This often leads to frustration becauseeven if customers tire of the expensive subscription fees, they arelocked into their contracts until the terms expire.

Moreover, due to the costs of these systems and the extensiveinstallation requirements (e.g., wiring, mounting of sensor hardware andpanels, integration with telecommunication systems, etc.), the securitysystems are generally only accessible to a certain segment of themarket, such as people who own their own buildings and have the freedomand money to have such systems installed therein.

Some current systems that use battery powered, wireless monitoringdevices to monitor a premises have either removed the ability to provideimages of security threats due to the typically computationallyexpensive processing required to capture, generate, and transmit theimages to the user devices of the stakeholders, or require stakeholdersto constantly charge or change the batteries in those monitoringdevices, which is frustrating to users and leads to low user adoptionand sales.

Other available solutions provide little to no control to the customers,and are thus less desirable. Rather, these solutions/security systemsoften operate blindly, relying on conventional timers and smoke alarms,to determine if threats exist. This can lead to the security systeminstallations triggering frequent false positive alarms, the remediationof which by the call centers or first responders can be very costly.These costs are often passed on down to the customers as well, therebyfurther exacerbating frustration of those customers.

SUMMARY

This disclosure describes technology that addresses the above-noteddeficiencies of existing solutions. In one innovative aspect, a securitysensor comprises a battery power supply, a camera, an activity sensor, aprocessor, and a microcontroller. The camera is coupled to the batterypower supply to receive power. The activity sensor is coupled to thebattery power supply to receive power. The activity sensor configured todetect activity within a zone proximate the security sensor. Theprocessor is placed in a sleep state and wakeable to an awake state. Theprocessor is coupled to the battery power supply to receive power, andcoupled to the camera to receive and process image data including imagesof the activity within the zone. The microcontroller is coupled to thebattery power supply to receive power, coupled to the activity sensor toreceive interrupts responsive to detection by the activity sensor of theactivity within the zone proximate the security sensor, coupled to theprocessor to send and receive data, and, responsive to receiving a firstinterrupt from the activity sensor, place the processor in an awakestate to signal the camera to capture a set of images and to receive andprocess the image data including the set of images.

In this or other aspects, the security sensor may additionally oralternatively include one or more of the following features: that theprocessor, upon being placed in the awake state, polls themicrocontroller for any events that occurred during the sleep state,determines a motion detection event occurred, sends a capture signal tothe camera, and receives and processes the image data including set ofimages; a non-transitory memory coupled to the battery power supply andthe processor; a transceiver coupled to the battery power supply, thememory, and the processor; that, responsive to receiving the image datafrom the camera, the processor caches the image data in thenon-transitory memory and the transceiver retrieves the image datacached in the non-transitory memory and transmits the image data to asecurity sensor relay for transmission to a security server accessiblevia the Internet; that the battery power supply, the camera when idle,the activity sensor when idle, the microcontroller, the processor whenin a sleep state, the non-transitory memory, and the transceiver whenidle, collectively draw a current of less than or equal to about 100micro amps; a non-transitory memory integrated with the microcontrollerthat stores state data including operational settings for the activitysensor; that, upon awaking the processor retrieves the state data fromthe non-transitory memory integrated with the microcontroller; that theprocessor operates on a sleep cycle and includes a sleep timer thatroutinely wakes the processor from the sleep state based on anexpiration of a sleeping period; that the sleeping period ispredetermined or dynamically set; that the activity sensor is a motionsensor configured to detect motion of a moving object within the zone;that the motion sensor is a passive infrared sensor; that the activitysensor is a smoke detector configured to detect smoke within the zone.

In another innovative aspect, a method for controlling operation of asecurity sensor, comprises: placing a processor of a security sensor ina sleep state, the processor being wakeable to an awake state and beingcoupled to a camera configured to capture a zone of a premises proximatethe security sensor; detecting with an activity sensor activityoccurring within the zone; receiving at a microcontroller a firstinterrupt from the activity sensor responsive to detection by theactivity sensor of the activity within the zone proximate the securitysensor; and responsive to receiving at the microcontroller the firstinterrupt from the activity sensor, placing the processor in an awakestate, signaling the camera to capture a set of images, and receivingand processing the image data including the set of images.

In this or other aspects, the security sensor may additionally oralternatively include one or more of the following features: uponplacing the processor in the awake state, polling, with the processorvia a communications bus, the microcontroller for any events thatoccurred during the sleep state; determining a motion detection eventoccurred; receiving image data including set of images at the processorfrom the camera and processing the image data; responsive to theprocessor receiving the image data from the camera, caching the imagedata in a non-transitory memory; retrieving using a receiver the imagedata cached in the non-transitory memory; transmitting the image data toa security sensor relay for transmission to a security server accessiblevia the Internet; that a battery power supply, the camera when idle, theactivity sensor when monitoring, the microcontroller, the processor whenin a sleep state, the non-transitory memory, and the transceiver whenidle, collectively draw a current of less than or equal to 50 microamps; storing state data in a non-transitory memory integrated with themicrocontroller; upon placing the processor in the awake state,retrieving using the processor the state data from the non-transitorymemory integrated with the microcontroller; operating the processor on asleep cycle; and routinely waking the processor from the sleep stateusing a sleep timer based on an expiration of a sleeping period; thatthe sleeping period is predetermined or dynamically set; that theactivity sensor is a motion sensor configured to detect motion of amoving object within the zone; that the motion sensor is a passiveinfrared sensor. In another innovative aspect, a method comprises:placing an image sensor of a security sensor in an inactive state, theimage sensor positioned to capture images of a zone proximate thesecurity sensor; receiving a user-initiated interrupt or anactivity-sensor-initiated interrupt from a microcontroller at the imagesensor; capturing using the image sensor a set of image frames of apotential threat within a zone proximate to a security sensor; sendingimages including the set of image frames to a processor; andtransmitting using a wireless transceiver the image data via a wirelessconnection to a security relay station. The method may additionally oralternatively include one or more of the following features: sensingusing a light sensor to determine available light within the zone;determining that a flash was not triggered during capture of the set ofimage frames based on the available light; triggering flash to alertpotential threat in the zone that the set of images frames werecaptured; retrieving image sensor settings from the microcontroller; andconfiguring the image sensor using settings.

Other embodiments of one or more of these aspects or other aspectsinclude corresponding systems, apparatus, and computer programs,configured to perform the various actions and/or store various datadescribed in association with these aspects. These and otherembodiments, such as various data structures, are encoded on tangiblecomputer storage devices.

The technology described herein provides numerous advantages includingmaximizing battery life of security sensors while automaticallydetecting security threats, automatically generating motion images ofthe threats and securely pushing them to the mobile devices of thestakeholders for review and assessment. The technology furtheradvantageously provides the stakeholders convenient countermeasureoptions for remediating the threats, providing hardware that is easy forusers to install and configure themselves, providing hardware that canbe installed in any building, which allows renters, lessees, and ownersalike to secure the buildings they live and work in, etc. It should beunderstood that the foregoing advantages and benefits are provided byway of illustration and that numerous additional advantages and benefitsare contemplated and encompassed by the scope of this disclosure.

It should be understood that the language used in the present disclosurehas been principally selected for readability and instructionalpurposes, and not to limit the scope of the subject matter disclosedherein.

BRIEF DESCRIPTION OF DRAWINGS

The disclosure is illustrated by way of example, and not by way oflimitation in the figures of the accompanying drawings in which likereference numerals are used to refer to similar elements.

FIG. 1 is a block diagram illustrating an example security systemenvironment.

FIG. 2 is a block diagram of an example architecture of a securitysensor.

FIG. 3A is a signal diagram of an example method for waking a processor.

FIG. 3B is a flowchart of an example method for operating a processor ona sleep cycle.

FIG. 4 is a flowchart of an example method for detecting a motion eventusing a motion sensor.

FIG. 5A is a flowchart of an example low-power method for capturing aset of images.

FIG. 5B is a flowchart of an example method for force flashing the flashof the camera to alert a potential intruder.

FIGS. 6A-6E depict example global variables that a microcontroller and amemory preserves during a sleep cycle of a processor.

FIG. 7 is a block diagram illustrating an example layout of a PS.

FIG. 8 is a signal chart illustrating an example charging cycle.

FIG. 9 is a flowchart of an example method for provisioning a low-powerprocessing device.

FIGS. 10A-10D are schematic diagrams depicting an example communicationbus that couples a processor 143 and a microcontroller.

FIGS. 11A and 11B are schematic diagrams of an example PS.

FIG. 12A is a perspective view of an example sensor.

FIG. 12B is a perspective view of an example relay station.

DETAILED DESCRIPTION

FIG. 1 is a block diagram illustrating an example security systemenvironment 100. The environment 100 may include one or more securityinstallations. Ideally, a multiplicity of users install the securityinstallations in various premises that they wish to monitor for securitythreats. A security installation may include a security relay station120 (also called a security gateway, a security base station, etc.) thatis linked to a set of one or more security sensors 140. As shown, theillustrated environment 100 further includes client device(s) 106 and aserver 160, which are electronically communicatively coupled via anetwork 102 for interaction with one another, the security relaystation(s) 120, and security sensors 140, etc., using standardnetworking protocols, as reflected by signal lines 104, 114, and 136. Ina typical installation, security sensor(s) 140 are coupled forelectronic communication with the security relay station 120 asreflected by signal line 134. In further embodiments, the securitysensor(s) 140 may be coupled directly to the network 102 as reflected bysignal line 138.

A security sensor 140 is configured to automatically detect securitythreats, capture image(s) of those threats, and relay the image(s) tothe security relay station 120 that the security sensor 140 is linkedto. The security relay station 120 is configured to manage the set ofsecurity sensors 140, and to exchange data with the management engine170 of the server 160. Users register with the security service embodiedby the management engine 170, which enables them to remotely configureand interact with their respective security installations, and toreceive security notifications automatically as threats are detected bytheir respective security installations.

In an example security installation, a stakeholder, such as a residentor a landlord, of the premises may install a relay station within thepremises (e.g., an office, the kitchen, etc.). The relay station 120 maybe connected to the network 102 (e.g., the Internet) via a modem and/ora router that is also installed at the premises, or may be wirelesslyconnected to the network 102 using a cellular connection. Thisconnection to the network 102 allows the relay station to communicatewith other elements of the environment, such as the server 160 and oneor more client devices 106. Within range of the relay station 120, thestakeholder installs corresponding security sensors 140 in one or morezones that are to be monitored (e.g., the entrance, living room,kitchen, washroom, rear entrance, etc.). Using a security application108, the stakeholder registers security sensors 140 with the relaystation 120 and the server 160, so that when the security sensors 140are powered on they can communicate and exchange data with the relaystation 120.

When armed, the security sensors 140 can detect the presence and/ormovement of an object (e.g., person) within the corresponding zones,capture image(s) of the person within a given zone, and relay thoseimage(s) (e.g., series of images) to the security relay station 120,which in turn, relays the image(s) via the network to server 160. Amanagement engine 170 operable by the security server 160 can receivethe images and generate a notification including the image(s) andprovide it to an instance of the security application 108 operating onthe client device 106 (e.g., mobile device) of the stakeholder who maybe in a location different from that of the premises, and the securityapplication 108 may alert the stakeholder and display the notificationincluding the image(s) (e.g., as a video or motion image) captured bythe security sensor 140 along with a user-selectable countermeasureoptions, such as “call 911”, “alert another user”, “turn on alarm”, etc.The management engine 170 may embody a remotely accessible securityservice. In further examples, the smoke detector 160 may trigger thecapture of images of a given zone upon detection of smoke within thatzone.

The security system has numerous advantageous as noted throughout thisdocument. For instance, its architecture minimizes current consumptionby the sensors 140. For example, among the numerous novel methodsdescribed herein, the sensor 140 is configured to put the transceiver(and other components) in deep sleep while the processor 143 issleeping, and save the state of transceiver's radio (and the othercomponents) so it does not have to reboot when reactivated (savingpower). Additionally, wakeup currents are also relatively low so in theevent of a reboot, minimal power is used. The system 100 may also beconfigured to store longer-term information on the security relaystation 120, which may be powered by the power grid and not necessarilya battery, which reduces the memory requirements (and thus powerrequirements) of the sensor(s) 140. Additionally, computationallyexpensive image processing may be performed on the relay station 120,the server 150, or the client device 106, thereby limiting the powerneeded to process the images. Many additional benefits and advantagesare also possible as discussed further elsewhere herein.

Further, sensor units that can trigger the capturing of the images andgeneration of a notification may include an accelerometer in the relaystation 120 or the security sensor 140, a moisture detection unit fordetecting moisture (e.g., flood, leaks, etc.) included in orelectronically coupled to the sensor 140, aperture (door, window, etc.)switches for detecting the opening/closing of a door that areelectronically coupled to a sensor 140, a glassbreak detector that iselectronically coupled to the sensor 140, or other security sensorunits. For instance, the sensor 140 may wake up and take a pictureand/or video on demand when tripped by a smoke detection event or glassbreak event or movement of one or more of the devices of the securityinstallation. These sensor units may be directly wired to the sensor 140or wirelessly connected (e.g., using the protocols discussed herein).

The example security sensor 140 depicted in FIG. 1 includes a powersupply (PS) 142, the processor 143, the memory 144, the microcontroller145, the memory 146, a set of sensors (e.g., the smoke sensor 150 a, themotion sensor 150 n, etc.), the camera 148, a transceiver 152, andoutput device(s) 155. The components 142, 144, 145, 146, 148, 150, 152,and 155 are communicatively coupled via a communications bus 158.

The security relay station 120 acts as an intermediate server thatcommunicates with both the remote sensor(s) 140 and the web-servicesprovided by the server 160. The security relay station 120 receives datafrom the sensor(s) 140 managed by it, processes that data in some cases,and relays the data to the server 160. The information from the server160 may be pushed to the security relation station 120 or may beprovided responsive to a request (polling) by the security relay station120. The security relay station 120 may store sensor settings for eachsensor 140 managed by it in the memory 126 and provide it to thesensor(s) 140 upon request.

An end user using an instance of the security application 108 may changesettings using an interface presented thereby, and the securityapplication 108 may synchronize those changes with the securityinstallation by sending them to the management engine 170 of the server160, which may store the settings in a data store in association withthe user and the security installation, and relay them to the securityrelay station 120. The security relay station 120 may update a statefile for each applicable sensor 120 in the memory 126. Upon receiving acheck-in signal from the sensor(s) 140 of the security installation, thesecurity relay station 120 relays the instruction to change thesettings. The processor 143 receives the instructions and instructs themicrocontroller 145 to update the settings. In some embodiments, the newsettings are updated in the memory 144.

As shown in FIG. 1, the security relay station 120 may include outputdevice(s) 122, a processor 124, a memory 126, a power supply (PS) 128,and an interface 130. The components 122, 124, 126, and 128 arecommunicatively coupled via a communications bus 134. In someembodiments, a security relay station 120 includes a communicationsdevice of communicating with a multiplicity of sensors, such as theinterface 130, a communications device of communicating with the server160 and computing devices 106 (e.g., a personal mobile device), such asthe interface 130), a non-transitory memory device for buffering andstoring messages, commands, responses, and measured data, such as thememory 126, a power source (e.g., PS 128), a mechanism to upgrade/changefirmware versions, an audio reproduction unit for playing sound bitesthat would be audible to living things within earshot of the gateway(e.g., the output device(s) 122), a microphone for recording sound bites(e.g., a microphone), computer-executable instructions (e.g.,software/firmware (e.g., a sensor management module) stored in thememory 126 and executable by the processor 124) for settingup/registering, managing the sensor(s) 140, and/or interacting with theserver 126, etc.

A further example architecture 200 of the security sensor 140 isdepicted in FIG. 2, although it should be understood that some of thehardware components (e.g., PS 128) are not shown so as not to obscurethe described aspects and that other suitable variations to thearchitecture are also possible and encompassed hereby.

As shown in FIG. 2, the sensor 140 uses a two-tier microprocessorcontrol system. The first tier processor, the processor 143, is aprimary processor and controls the high-level functioning of thesecurity sensor 140. The second tier processor, the microcontroller 145,is an ultra-low power peripheral interface controller (PIC) thatincludes memory that maintains a persistent state through deep sleep.The microcontroller 145 controls the lower-level peripherals andfunctions (e.g., the sensors 150, the siren 155, battery level polling,etc.). A non-limiting example of the processor 143 is a SAM4S Cortex™-M4processor-based microcontroller by Atmel™, although it should beunderstood that other processors suitable to carry out the acts andfunctionality discussed herein are also possible and contemplated. Annon-limiting example of the microcontroller 145 is a PIC18(L)F2X/4XK22made by Microchip™, although it should be understood that otherprocessors suitable to carry out acts and functionality discussed hereinare also possible and contemplated.

The microcontroller 145 can monitor interrupts received by the sensors150 while operating in a low-power mode and the processor 143, whichuses more power than the microcontroller 145 when active, can be putinto a deep sleep (also just called a sleep), which allows the securitysensor 140 to achieve superior battery life relative to existingsolutions. The ultra-low sleep/energy state of processor 143 while inthe deep sleep mode limits the current drain from the battery, thusincreasing the life of the sensor 140's battery. In other words, thetwo-tier microprocessor system consumes a very low amount of power(e.g., in some ideal embodiments less than 1 μamp, about 1-10 μamps,and/or about 10-100 μamps, but also including 100 μamps-100 milliamps orother ranges depending on the implementation and power requirements,during inactive periods) to maintain the system without requiring systemreconfiguration or recalibration of the system when returning to awakened, executional state. It should be understood that the term aboutor substantially means the current may be within 2-5 units of thedescribed amount or range. In some embodiments, the collectivecomponents of the sensor 140 (e.g., the battery power supply 142, thecamera 148 when idle, the activity sensor(s) 150 when monitoring, themicrocontroller 145, the processor 143 when in a sleep state, the memory146, and the transceiver 152 when idle) draw a current less than orequal to 10 μamps.

By way of example but not limitation, using 4 AA NiMH rechargeablebatteries, the security sensor 140 can achieve 1-2 years under typicalconditions, which is advantageous as it alleviates stakeholders fromhaving to constantly charge batteries or requiring the sensor 140 to beinstalled near a power source, making it easily mountable and suitablefor rental units, extended stay suites, and other shorter durationstays, although other applications also apply and are contemplated.

As discussed further elsewhere herein, the processor 143 wakes up fromthe low energy state periodically (e.g., every 3, 4, 5, 6, 10, 12, etc.)seconds and checks in with the relay station 120 to see if there are anyrequests/commands. In some instances, this process can take about 20 ms,although it is contemplated that this could be shorter or longer. If theprocessor 143 receives any requests/commands from the relay station 120,the sensor processes them and reports back to the relay station 120 withappropriate data. If there are not any, the processor 143 goes back tosleep.

When disarmed, the processor 143 ideally places all possible thecomponents 145, 148, 150, 155, etc., in sleep or off state asappropriate. When armed, the processor 143 wakes/arms the applicableactivity sensors 150 (e.g., the motion sensor 150 n and/or the smokesensor 150 a). In some embodiments, the sensors 150 even when activatedare in a low power detection mode to preserve power. If motion or smokeis detected, a wake up interrupt wakes up the processor 143, asdiscussed further herein, which in turn activates the camera/imagesensor 148 (e.g., warms up and snaps a set of images (e.g., 1-5, etc.)via the microcontroller 145 pictures. Similarly, in an embodiment wherethe sensor 140 includes a sound capture device (e.g., microphone), themicrocontroller 145 may trigger the image capture process if the soundlevels are higher than an acceptable threshold and the security sensor140 is armed. Other variations are also possible and contemplated.

The microcontroller 145 and the processor 143 may be coupled via aportion of the communications bus 158. The processor 143 may signal themicro controller 145 via the bus 158 to execute certain actions, such asturn various devices on or off, arm or disarm various devices, etc. Forinstance, as shown the processor 143 may send the microcontroller 145and on signal 201, and off signal 202, an arm signal 203, and a disarmsignal 204. Additionally, the processor 143 may poll 205 themicrocontroller 145 for any events that may have occurred while theprocessor 143 was sleeping, which may include motion detection events,smoke detection events, noise events, other sensor events, power supplyevents, hardware failure events, etc. For instance, in response to amotion detection event, the processor 143 may signal the microcontroller145 to activate the camera 148, and the processor 143 may receive andprocesses the image data including set of images from the camera 148 inresponse. In some instances, the processor 143 polls the microcontroller145 responsive to receiving an interrupt 206.

In further embodiments, the security relay station 120 may include anaccelerometer to detect movement of the security relay station 120. Theprocessor 124 is coupled to the accelerometer and monitors the readingsthereof. If the readings indicate that the security relay station 120 isbeing picked up, it may send a notification to the server 160 of themovement, and the server 160 may send a notification to the securityapplication to notify the user of the movement (e.g., via a pushnotification, interface presented on the device, an electronic message,etc.).

FIGS. 10A-10D are schematic diagrams depicting an example communicationsbus 158 that couples the processor 143 and the microcontroller 145. Asshown, SIO_D and SIO_C 1002 comprise an I2C bus which connects theprocessor 143 to the microcontroller 145. The PIC_TO_SAM_WAKEUP 1004 isa line connecting the processor 143 and the microcontroller 145. Themicrocontroller 145 can send a wakeup signal/interrupt via thePIC_TO_SAM_WAKEUP 1004 to wake up the processor 143. It is noted thatthe schematics depicted in FIGS. 10A-10D are provided by way of examplethat that other suitable bus configurations are also contemplated andencompassed by this document.

The processor 143 may store and retrieve settings 207 in the memory 144associated with the microcontroller 145, as discussed further elsewhereherein. In some embodiments, the memory 144 is embedded in themicrocontroller 145, although it should be understood that in othercases, the memory 144 may be separate from but coupled to themicrocontroller 145 and the processor 143, provided the powerconsumption and performance of the memory is similar.

As noted above, the microcontroller 145 controls the peripheralcomponents of the sensor 140. Example peripheral components are depictedin FIGS. 1 and 2, although it should be understood that other peripheralcomponents are also possible and contemplated, as discussed elsewhereherein. In the depicted embodiment, the microcontroller controls thesmoke sensor 150 a, the siren 155, the motion sensor 150 n, the camera148, etc.

For example, the microcontroller 145 can signal the smoke sensor 150 ato arm 208 and to disarm 209, and to the motion sensor 150 n to arm 214and to disarm 215. Responsive to detecting activity within the zonebeing monitored, the smoke sensor 150 a can send an interrupt signal 210to the microcontroller 145 indicating that it has been tripped, and themotion sensor 150 n can send an interrupt signal 216 to themicrocontroller 145 indicating that it has been tripped. As depicted, insome embodiments microcontroller 145 may configure the settings of smokesensor 158 and/or the motion sensor 150 n by storing various settings(e.g., operational parameters) in the memory of the smoke sensor 150 aand/or the motion sensor 150 n, and or setting corresponding registersthereof. The microcontroller 145 can signal the siren to turn on 211 andturnoff 212. In addition, microcontroller 145 can send a duration signalto the siren 155 indicating a duration for which the siren should emitsound once turned on. This duration can be stored in a register of thesiren 155 in some embodiments, although other variations are alsopossible and contemplated.

The microcontroller 145 can turn the camera 148 on and off by sending itan on signal 217 and an off signal 218 to turn it on and off,respectively. When turning it on, the microcontroller 145 and/or theprocessor 143 can send the camera 148 operational settings to configurethe function and performance of the camera 148. For instance, theprocessor 143 (or the microcontroller 145 in some embodiments) cansignal the camera 148 to capture one or more images by sending a capture223 signal. When the image sensor of the camera 148 captures image data,it sends the image data 219 to the processor 143, which in turn cachesthe image data 219 in the memory 146 for transport to the security relaystation 120. For instance, the transceiver 152 retrieves the image data219 from the memory 146 and sends it to the security relay station 120as outgoing data 222. Additionally, the transceiver 152 sends incomingdata 220 to the processor 143 (e.g., responsive to a check-in 221).

FIG. 3A is a signal diagram of an example method 300 for waking theprocessor to capture image data responsive to a detection event by amotion sensor 150 n. As shown, the processor sleeps and awakes accordingto a schedule. In this example, the processor 143, which is power hungryrelative to at least some of the other components of the security sensor140, is asleep to the extent possible to preserve power. As discussedbelow, the processor 143 wakes up periodically to perform various tasks(e.g., re-enable the power supply to keep the processor 143 alive, takea picture, turn on the siren 155, receive information about an event(e.g., motion detected by the motion detector 150 n), etc.).

The time t_(p) illustrates an example periodicity of the sleep cycle,which includes an active time t_(a) during which the processor 143 isactive and a sleep time t_(s) during which the processor 143 issleeping. In this embodiment, the camera 148 is coupled to a batterypower supply (e.g., PS 142) to receive power, and an activity sensor 150(e.g., the motion sensor 150 n) is coupled to the battery power supplyto receive power and is configured to detect activity within a zoneproximate the security sensor.

In the embodiment depicted in FIG. 3A, the processor, during t_(a),sends an instruction signal 301 to the microcontroller (e.g., to turn onthe motion sensor 150 n). In an example, this could be responsive to auser enabling the motion sensor 150 n in an instance of the securityapplication 108 operating on his/her client device 106, state settingsreceived from the security relay station 120 upon power on, or the like.After sending the signal 301 to the microcontroller 145, the processor143 sleeps.

Responsive to receiving the signal 301 from the processor 143, themicrocontroller 145 sends an on signal 302 signaling the motion sensor150 n to turn on. The motion sensor 150 n switches from a sleep/offstate to an awake/on state and begins monitoring the zone proximate thesecurity sensor for movement.

After a period of time, the motion sensor 150 n detects a motion eventand sends an interrupt 303 to the microcontroller 145, which uponreceiving the interrupt 303, sends a corresponding interrupt 304 to theprocessor 143 to wake the processor 143. In this example, the processor143 is awakened during its usual sleep cycle responsive to the detectionby the motion sensor 150 n of a motion event. As discussed elsewhereherein, responsive to receiving the interrupt 304, the processor 143 canpoll the microcontroller 145 for any new events to determine the reasonfor the interrupt and then act accordingly.

Further, the microcontroller 145 turns on the camera by sending a cameraon signal 305 to the camera 148, which, upon receiving the signal 305,awakes. The processor 143 and/or the microcontroller 145 may then sendone or more commands/settings 306 (e.g., capture command, configurationparameters, etc.) to the camera 148 which the camera uses to configureand/or control itself. Then the camera 148 captures image data includinga set of images of the zone being monitored and sends the capture/imagedata 307 to the processor 143, which is now awake responsive to theinterrupt 304 and which relays 308 the image data for transmission tothe security relay station 120.

FIG. 3B is a flowchart of an example method 310 for operating theprocessor 143 on a sleep cycle. As discussed elsewhere herein, thesleeping period of the cycle may be predetermined or dynamically set insome cases. In block 312 of the method 310, the processing functions ofthe processor 143 are turned off, various system settings are stored 314in the memory of the microcontroller 145, and the volatile memory of theprocessor 143 largely discharges 316 because the amount of voltagesupplied to its internal memory is substantially reduced. Powering downthe volatile memory of the processor 143 is advantageous because itpreserves battery life. The system settings (e.g., state of the system,user-defined characteristics (e.g., arm/disarm state, PIR sensitivitylevel, smoke detection on/off, radio power, provisioning information)are stored in the memory (e.g., flash memory) of the microcontroller.

In block 318, a wake event is detected. For example, a sensor-initiatedinterrupt is received by the processor 143 or a sleep timer wastriggered based on the expiration of a sleeping period. Responsive tothe wake event, the processor 143 is placed in an awakened state andretrieves and loads 320 system settings (e.g., state data, etc.) fromthe memory 144 of (e.g., integrated with) the microcontroller 145, andthe processor 143 executes 322 the event (e.g., takes picture(s) usingthe camera 148, triggers a notification to the user, etc.).

FIG. 4 is a flowchart of an example method 400 for detecting a motionevent using a motion sensor 150 n. In the description of this method400, a passive infrared sensor is used, although it should be understoodthat other sensors that are capable of detection motion are alsopossible and contemplated, and that the method is also suitable forother types of sensors that detect conditions (e.g., light, smoke,noise, vibration, etc.).

In block 402, the microcontroller 146 powers the passive infrared sensor(PIR) sensor responsive to receiving a corresponding instruction fromthe processor 143. In block 404, the microcontroller 145 configures thesettings of the PIR sensor in the local memory of the PIR sensor. Thesettings may, in some cases, include a sensitivity threshold. In block406, the PIR sensor determines whether a movement it detected satisfiesthe settings (e.g., sensitivity threshold), and if so, in block 408, thePIR sensor sends an interrupt to the microcontroller 145 notifying themicrocontroller 145 of the motion detection event.

FIG. 5A is a flowchart of an example low-power method 500 for capturinga set of images. In block 502, the processor 143 of the security sensor140 is placed in a sleep/inactive state. In block 504, if the processor143 receives an activity sensor-initiated interrupt, the processor 143activates the image sensor 148 via the microcontroller 145 in block 508.For example, if the microcontroller 143 receives an interrupt from themotion sensor 150 n or the smoke sensor 150 a (after detecting activityoccurring within the zone being monitored), then the microcontroller 145sends an interrupt to the processor 143. Alternatively, in block 506, ifthe processor 143 receives a user-initiated interrupt (as relayed fromthe server 160 to the sensor 140 by the relay station 120), theprocessor 143 activates the image sensor 140 via the microcontroller 145in block 508.

In block 510, the image sensor 148 receives one or more configurationsettings from the microcontroller 145 and/or the processor 143. In someembodiments, the microcontroller 145 and/or the processor 143 configuresthe registers of the image sensor 148 to set its operational parameters.In some further embodiments, the image sensor 148 may receive andprocess the settings and set its own parameters. In some embodiments,the image sensor 148 is already configured and block 510 may be skipped.

In block 512, responsive to receiving a capture command, the imagesensor 148 captures a set of calibration image frames. The image sensor148 of the processor 145 may, in block 514, use the calibration imageframes to calibrate the operational parameters of the image sensor 148,such as aperture settings, focal length, and whether to trigger theflash during capture, etc.

In block 516, the image sensor 148 captures a set of image frames over aperiod of time of the potential threat within the zone of the premisesbeing monitored. Responsive to the set of image frames being captured,the image sensor 148 sends, in block 518, image data including a set ofimage frames to the processor 143, which is in an awake state andreceives and processes the image data including the set of images.

In block 520, the processor 143 processes the image data by at leastcaching it in the memory 146 and block 520, and the transceiver 152retrieves the image data from the memory and transmits it to thesecurity relay station 122. The security relay station 122 receives theimage data related to the server 160 for communication to the user viathe security application 108, as discussed elsewhere herein. To optimizepower savings, processing by the processor 143 of the image data may beminimized by shifting any computationally expensive image processingrequirements to other devices such as the security relay station 120,the server and 160, and/or the client device 106.

In some embodiments, while the processor 143 is caching the image datain the memory 146, the transceiver simultaneously retrieves it from thecash and transmits it. In these embodiments, the memory 146 is acting asa staging area for the image data, and once it is safely transmitted tothe security relay station 122, the image data may be wiped from thememory 146. However, having it cached in the memory 146 is advantageousshould any of the packets of image data being transmitted by thetransceiver 152 to the interface 130 of the security relay station 122become corrupted or lost, as those packets of image data canconveniently be retrieved and transmitted again. By way of example, thememory 146 may be configured to store up to a certain number of images(e.g., 3, 4, 5, etc.) while awaiting transport, etc., although it shouldbe understood that any number of images required may be stored.

FIG. 5B is a flowchart of an example method 550 for force flashing theflash of the camera 148 to alert a potential intruder. In block 504, thecamera 148 and/or the processor 143 determines whether the flashtriggered during the image capture of block 518. If the flash did notfire during the capturing of the images and block 518, the camera 148fires/triggers 554 the flash after the capturing of the images. This isbeneficial as it repurposes the flash as an alert beacon alerting apotential intruder that their presence has been detected, as well assignaling to a stakeholder (e.g., homeowner, etc.) that a picture hasbeen taken for security reasons.

In some embodiments, the camera 148 can determine whether to fire theflash when capturing a certain set of images at a certain time byevaluating the available light in the zone being monitored using a lightsensor (e.g., Lux sensor, photodiode, etc.). The camera 148 and/or theprocessor 143 can read the level detected by the light sensor, compareit to previously determined light thresholds (e.g., high, medium, low,etc.), and determine to fire the flash if the light level is at or belowa certain one of thresholds (e.g., med, low, etc.). Therefore, if theambient light in the room is sufficient to capture a photo without theflash, the camera 148 will capture the set of images, and then triggerthe flash after the images are captured. Alternatively, the camera 148may trigger the flash before the set of images are captured at a pointearly enough that the flashed light has dissipated and does not affectthe set of images being captured.

If it is determined that the flash is needed during image capture, thecamera 148 and/or the processor 143 may internally calibrate and adjustthe flash (e.g., LED(s)) are internally calibrated and adjusted to lightup for only the optimal length of time in order to illuminate the sceneas necessary while still preserving battery life. For example, if duringa comparison between the light level reading and the predeterminedthresholds, it is determined that a low amount of light is available inthe zone being monitored, the flash may be calibrated to light up forlonger than if a medium amount of light is determined to be available inthe zone being monitored. Thus, daytime pictures may use less flash andbattery power than those taken in a dark room.

With reference again to FIGS. 1 and 2, the buses 134 and/or 158 caninclude a communication bus for transferring data between components ofa computing device or between computing devices, a network bus systemincluding the network 102 or portions thereof, a processor mesh, acombination thereof, etc.

The transceiver 152 includes a wireless interface configured tocommunicate with the security relation station 120, and or othercomponents of the network 102. In some embodiments, the transceiver 152of the sensor 140 may include a wireless transceiver configured totransmit data via a meshwork network made up of a plurality of sensors140 and a security relay station 120. By way of further example, thetransceiver 152 may transmit data to the relay station 120 to which itis linked using a protocol compliant with IEEE 802.15, such as Zigbee®,Z-Wave®, Bluetooth®, or another suitable standard. Conversely, theinterface 130 of the relay station 120 may transmit data to the sensor140 using a corresponding protocol. In further embodiments, one or moreof the sensor(s) 140 and the relay station 120 of an installation becoupled to the network 102 (e.g., the internet via Wi-Fi™) forcommunication with one another using protocols discussed elsewhereherein. Additionally or alternatively, one or more of the sensor(s) 140and the relay station 120 of an installation may be wired for directcommunication and the wired components may exchange data using wireddata communication protocols. Further embodiments are also possible andcontemplated.

In some embodiments, the transceiver 152 of a sensor may include anadjustable power radio transmitter that adapts signal power according todistance from the security relay station 120 and signal strengthrequired. This prolongs the battery life of the sensor so that a sensor140 near a relay station 120 does not waste extra battery power totransmit signals to the relay station 120 while simultaneously allowinga sensor 140 located further away from the relay station 120 to stillcommunicate reliably therewith. In addition, the adjustable power radiotransmitter is a good neighborly wireless device because it can limitthe amount of signal noise produced when signaling to only what isnecessary to maintain a reliable connection to the relay station 120,thereby dramatically reducing excess signal noise that other networkinghardware devices emit indiscriminately.

In some embodiments, the transceiver 152's radio's throughput is set toa certain threshold (e.g., 250 kbps) allowing the radio to consume verylow power, while still maintaining the ability to transmit pictures overthe RF line. In conjunction with the other power saving featuresdiscussed herein, the security sensor 140 can, by way of example,operate for more than a year without requiring charging or a batterychange.

In some embodiments, the relay station 120 (and/or sensor(s) 140) maytypically communicate via the network 102 via a WLAN, but when a powersurge occurs or the connection to the network 102 (Internet) isdisrupted in some way, the relay station 120, as a fallback, may coupleto and transmit data via the network 102 using a connection to a datanetwork (e.g., WWAN) of a mobile network (e.g., via a 3G, 4G, 5G, etc.).In these embodiments, the relay station 120 may include a backup batterythat allows it to continue operating even though wired power to thedevice(s) was interrupted.

The interface 130 can transmit and receive data to and from otherhardware components and computing devices to which they are coupled. Theinterfaces 130 may be coupled (wiredly, wirelessly, etc.) to otherhardware and/or the network 102 to communicate with other entitiesforming the network 102. In some embodiments, the interface 130 mayinclude one or more wireless transceivers for exchanging data with thetransceiver 152 and other components of the environment 100 using one ormore wireless communication methods, including TCP/IP, HTTP, HTTPS,WebSockets, IEEE 802 (e.g., 802.11, 802.15, IEEE 802.16, etc.),dedicated short-range communications (DSRC), or other suitable wirelesscommunication methods as discussed elsewhere herein. In someembodiments, the interface 130 can include a cellular communicationstransceiver for sending and receiving data over a cellularcommunications network including any generation (3G, 4G, 5G+, etc.)mobile network.

In some embodiments, the interface 130 of the relay station 120 of agiven installation is coupled to the network 120 (e.g., the Internet)and thereby further coupled to the server 160 to exchange data with themanagement engine 170 operable thereby, as discussed elsewhere herein.

In some embodiments, the interfaces 130 and/or 152 may include one ormore ports for direct physical connection to the network 102 or toanother communication channel. For example, the interfaces 130 and/or152 may include a USB, SD, CAT-type, Thunderbolt, or similar ports forwired communication with other hardware, such as memory devices,computers, etc. For instance, the interfaces 130 and/or 152 may includea removable memory card slot configured to receive a compatiblesolid-state memory card storing data and/or software executable by therelay station 120 to perform various acts and/or functionality asdiscussed elsewhere herein. For instance, the memory 126 and/or 146 mayresemble a removable type memory coupled to the interfaces 130 and/or152, respectively, although further embodiments are also contemplatedwhere the security relay station 120 and/or security sensor 140additionally or alternatively includes more permanent memory devices.

The output device(s) 122 and/or 155 may include one or more devices forrelaying information. In some embodiments, the output device(s) mayinclude auditory or visual output devices 155 for communicating withand/or alerting people, such as lights, audio reproduction units (e.g.,speakers), a visual display (e.g., an e-ink display, LED display,touchscreen, etc.), etc. As a further example, the output device(s) mayinclude the siren 155 or buzzer, a flash or strobe light, and/or thelike, for alerting nearby individuals that a security alarm has beentriggered, an intercom or speaker for relaying voice communications fornotifying an individual (e.g., an intruder) that countermeasures havebeen taken and/or demanding an individual (e.g., an intruder) leave thepremises, etc.

In some embodiments, the output device(s) 122 and/or 155 may play one ormore sound bites audible to living things within earshot of the sensor140. In this example, the sound bites (e.g., various siren notices,warnings, etc.) could be pre-installed by the manufacturer or may beuser-defined. For instance, the user may record a sound bite using afeature of the security application 108 in conjunction with a microphoneof the client device 106, and the security application 108 may uploadthe sound bite to the management engine 170, which in turn, may transmitthe sound bite to the security relay station 120 and/or the securitysensor(s) 140 for storage and playback. The user could additionally oralternatively record the sound bite using a sensor (e.g., microphone) ofthe security relay station 120 and/or the security sensor(s) 140. Inthis example, the sensor may include a button selectable by the user toinitiate the sound bite recording process provided by the processor 143,which may capture and store the sound bite on the memory 146 and/or 126for later playback. Other variations are also possible and contemplated.In some cases, different sound bites for different situations (e.g.,fire detection, CO detection, intruder detection, etc.) may be used.

As discussed elsewhere herein, the microcontroller 145 and/or theprocessor 143 may be programmed with/executes computer logic (e.g., adetection, capture, and processing module) to interpret the signals anddetermine, based on the signals, whether any security threats exist, asdiscussed elsewhere herein.

In further examples, the security relay station 120 and/or securitysensor(s) 140 may include a hardware button selectable by a user todisarm the security installation. For instance, if an administrativeuser (e.g., parent) is not available, a child (e.g., who may not haveaccess to a computer (e.g., client device 106) but knows where the relaystation 120 is located may disarm the security installation by pressinga button or series of buttons (e.g., entering a pin), etc.

The camera 148 includes a digital image capture device capable ofcapturing still and motion images, and sound. The camera 148 is coupledto the bus 158 for communication and interaction with the othercomponents of the sensor 140. The camera may include a lens forgathering and focusing light, a photo sensor including pixel regions forcapturing the focused light and a processor for generating image databased on signals provided by the pixel regions. The processor may beintegrated with the microcontroller 145 and/or the processor 143 of thesensor 140 or may be separate therefrom. In some embodiments, theprocessor of the camera 148 is coupled via the bus 158 to store imagedata in the memory 146. The photo sensor may be any type of photo sensorincluding a charge-coupled device (CCD), a complementarymetal-oxide-semiconductor (CMOS) sensor, a hybrid CCD/CMOS device, etc.The camera 148 may include a microphone (not shown) for capturing soundor may be coupled to and interact with a microphone included as a sensor150 of the sensor 140. The camera 148 may also include any conventionalfeatures including flash, a zoom lens, etc.

As a further non-limiting example illustrating the operation of thecamera 148, responsive to a trigger event, the camera 148 of thesecurity sensor 140 captures a series of images (e.g., 3-5), which arethen transmitted to the relay station 120 and the server 160. When morethan one image is captured, it comprise a motion image or may becombined into a motion image, such as an animated GIF or HTML5 video.These images may be combined at any point during the transmission fromthe security sensor 140 to the client device 106, which displays thecombined images to the user. For example, hardware and/or software logicexecuted by the camera 148, the microcontroller 143, the processor 146,the processor 124, the server processor, or a processor of the clientdevice 106 may generate the motion image, although not performing theprocessing using the components of the security sensor 140 isadvantageous from a power-saving perspective. In further variations, theimages may be uncombined and transmitted and/or displayed to the user inseparate form and/or flipped through by the user as such.

In some embodiments, the camera 148 is programmed to be in deep sleepfor periods of inactivity in the monitored zone (which may extend fordays, weeks, etc.) to maintain battery life. By way of example, theimage sensor/camera 148 can be activated with an interrupt from themicrocontroller when motion, smoke, or other conditions are detectedwhile the system is armed or when the user requests an image on demand,as discussed elsewhere herein. Sleeping the camera in this way isadvantageous as it conserves considerable battery life relative tokeeping the camera in an awake state.

When the sensor is activated, the camera immediately begins aself-calibration routine capturing several frames of picture/video andself-stabilizing to optimize its register settings. The camera 148 maycapture any number of images over a set period of time at pre-configuredintervals, and may be calibrated/optimized as discussed elsewhereherein. In some embodiments, the processor 143 may configure the camera148 by setting various registers of the camera 148. The registers mayalso be optimized using calibration frames captured prior to the primarycapture of image data of the detected anomaly.

In further embodiments, the memory 146 may store a camera drivercomprising software executable by the microcontroller 145 and/or theprocessor 143 to control/operate the camera 148. For example, driver maybe executable by the microcontroller 145 and/or the processor 143 forsignaling the camera to capture and store a still or motion image andcontrolling the flash, aperture, focal length, etc., of the camera 148.The detection, capture, and processing module may interface with thedriver (e.g., using APIs) to capture still and/or motion images usingthe camera 148. In some further embodiments, the driver may be includedin the detection, capture, and processing module.

The activity sensor(s) 150 (or just sensors 150) include various sensorsfor detecting sound, motion, temperature, light, heat, gas, vibration,etc. The signals from the sensor(s) 150 may be received and interpretedby the detection, capture, and processing module to determine if athreat is posed, as discussed elsewhere herein. In some embodiments, thesensor(s) 150 may include passive infrared (PIR) sensors,photodetectors, luminosity sensors, heat detectors, pressure sensors,optical detectors, electrochemical sensors, audio sensors (e.g., sounddetector, microphone, level meters, etc.), thermocouples, etc.

In some embodiments, one or more motion sensors 150 a sensors may beincluded in the security sensor 140 to detect motion of objects withinthe field of view of the PIR sensor.

In some embodiments, the motion sensor(s) 150 a are PIR sensor(s),although other motion sensors are applicable. The PIR sensor may have acertain detection range and angle. A non-limiting example range may beabout 0-50 ft and a non-limiting example detection angle may be about±50 degrees, although other ranges and angles are also possible (e.g.,about 5-45 ft, about 0-30 ft, about 0-100 ft, about ±30, 45, 49, 90degrees, etc.), etc.

The PIR sensor(s) may have a configurable switching threshold that befrom between 0% and 100%. The microcontroller 145 (e.g., in cooperationwith other components) may configure the switching threshold by sendinga threshold (re)setting instruction to the PIR sensor(s). Additionallyor alternatively, the PIR sensor(s) may include a hardware element(e.g., switch, potentiometer, button, etc.) for a user to manually setthe threshold. In some embodiments, a 0% or no switching threshold maybe set and the microcontroller 145 may determine or utilizeuser-determined and/or predetermined switching thresholds for triggeringa security threat, as discussed elsewhere herein.

User-adjustable settings for the PIR may be stored as system settings inthe memory 126, 144, etc. Selecting this component for motion detectionallows the security sensor 140 (e.g., the two-tier microcontrollercontrol system) to stay in deep sleep mode while the PIR sensor isalways on. When a trip event occurs or motion is detected, the PIRsensor will send an interrupt to the processor 143 via themicrocontroller 145 to enable all of the system commands and settingsneeded to take pictures, enable the siren, and notify the user, etc. Insome embodiments, the PIR can provide digital output to themicrocontroller 145 and includes registers that can be programmed andtuned to adjust sensitivity, as discussed elsewhere herein.

The PIR sensor(s) may be coupled to the bus 158 to transmit signals tothe microcontroller 145 and/or the processor 143, which executescomputer logic (e.g., the detection, capture, and processing module) tointerpret the signals and determine, based on the signals, whether anysecurity threats exist, as discussed elsewhere herein.

The smoke sensor 150 is configured to detect the presence of smokewithin the monitored zone. In some embodiments, for ultra-low powerconsumption, a two-part optical smoke sensor 150 is used that comprisesan LED and photodiode to detect the presence of smoke. In someembodiments, the smoke sensor 150 includes chamber for smoke to enterinto. One side of the chamber includes an infrared emitter and anopposing side includes an infrared detector. The emitter and detectorare angled with respect to each other so that when the chamber is voidof smoke the detector is unable to see the light coming from theemitter. When smoke enters the chamber, it causes the light from theemitter to refract and find a path to the detector.

The smoke sensor 150 a also includes an integrated microcontroller toprocess and check for air quality, smoke, self-test and other functions.This microcontroller is coupled to the emitter and detector. When thedetector detects light from the emitter (i.e., detects the smoke), itsignals the microcontroller, which, in turn, signals the alarm, andnotifies the microcontroller 145 about the threat. This allows securitysensor 140 to stay “aware” of potential threats while the processor 143and the microcontroller 145 are in a sleep state to prolong batterylife. This is further accomplished without the security sensor 140becoming uncalibrated.

As discussed elsewhere herein, in a typical scenario, the sensor 140operates on battery power, and as a result, conserving energy used bythe sensor 140 during monitoring becomes increasingly important toreduce the need by the user to replace or charge the battery. Whenactive, the PIR sensor requires a consistent (e.g., continuous, pulse,etc.) electrical current for operation. Even though the current istypically extremely low (e.g., 1.6 mA@3.3V), regulating the current witha power regular can consume more power than desired and reduce thestandby duration of the battery. For instance, the power regulator, whenstepping down the power to the required current for the PIR sensorconsumed significantly more power (e.g., 3×, 4×, 5×, etc.) than the PIRsensor itself.

Advantageously, the PS 142 includes a set of one or more capacitorsdownstream of the power regulator and upstream of the PIR sensor, asdiscussed below with reference to FIG. 7, for example. In thisembodiment, the capacitor(s) collects power from the power regulator,and when the capacitor is fully charged, the power regulator shuts off(thus conserving power), and the PIR sensor receives current from thecapacitor instead of directly from the power regulator. When the amountof charge in the capacitor starts to get low, the power regulator turnsback on and recharges the capacitor, as discussed further below.

FIG. 7 is a block diagram illustrating an example layout of the PS 142.As shown, the architecture includes a battery 700, a power regulator 702connected to the battery 700 downstream of the battery 700, a first setof capacitors 706 connected downstream of the power regulator 704 andproviding power to the processor 143 and the microcontroller 145, andthe other components 144, 146, 150 a, 150 n, 148, 152, 155, etc., and asecond set of capacitors 702 situated upstream of the regulator 702 anddownstream of the battery 700. The configuration depicted in FIG. 7further allows the security sensor 140 to prolong battery life.

The battery 700 may include any suitable battery or array of batteries.The batteries may be rechargeable or conventional disposable batteries.Operating solely on battery power is advantageous because it enables thesecurity sensor 140 be mounted virtually anywhere without having to plugthe security sensor 140 into a fixed power source (e.g., a correctionalelectrical plug). It is noted that in addition or as an alternative tothe battery, other native power sources may be utilized, such as a solarcell, and/or wireless-charging technologies (inductive charging, etc.)may be employed to power the sensors 140 without departing from thescope of this disclosure.

During a charge cycle, the power regulator 704 is switched off until alow charge threshold of the first set of capacitors 706 has beenreached, and once the low charge threshold has been satisfied, the powerregulator 704 switches on to charge the first set of capacitors 706until a high charge threshold has been reached.

FIG. 8 is a signal chart illustrating the charging cycle 800 of thefirst set of capacitors 706. As shown, the first set of capacitors 706store sufficient energy to power the system during a sleep cycle (e.g.,over 3 volts, 4 volts, etc.). Current is drawn from the bank ofcapacitors 706 over time to maintain the sleep state of the securitysensor 140. As the capacitor charge dissipates and the low threshold isreached (as monitored by the microcontroller 145), the power regulator704 activates and charges the first set of capacitors 706, as shown bycycles 802 and 804.

The second set of capacitors 702 maintain the state of the powerregulator 704 and allow the power regulator 704 to draw the requisiteamount of current when powering on without impacting the battery 700.For example, The battery 700 may have an internal resistance, and when alarger amount of current needs to be drawn than the battery 700 cansupply at a given point (switching on of the power regulator 702), thesecond set of capacitors 702 provide a reserve for that surge in currentconsumption by the power regulator 704.

The power regulator 702 down-converts the voltage from that supplied bythe battery 700 to the level that the microcontroller 145, the processor143, and other system level components require. FIGS. 11A and 11B areschematic diagrams of an example PS 142. In the depicted architecture1100, the power regulator includes a buck regulator configuration,although other variations are also possible and contemplated.

Using the power regulator 702 allows the sensor 140 to operate solely onbattery power. However, while the power regulator 702 is running, italso consumes electricity. To reduce this current draw, the first set ofcapacitors 706 are placed downstream from the power regulator 702. Theset of capacitors release current over time to the required componentsat the appropriate voltage allowing the power regulator 702 to be offfor extended periods of time, particularly during idle periods (nodetection or image capture events).

The PS 128 may include a regulated power supply (e.g., AC power supply),a transformer (AC/DC converter), one or more energy storage devices(e.g., a rechargeable batter(ies), non-rechargeable batter(ies)),wiring, etc., wireless charging units (e.g., inductive charging units(e.g., induction coils)). In some embodiments, the PS 128 may includeregulated power supply that can be plugged into a fixed power source,such as a conventional logical plug, because the security relay station120 may not need monitor a particular zone and therefore can beimmediately placed next to any electrical outlet.

In some embodiments, an audio sensor may embody hardware for recordingsound bites as discussed elsewhere herein, or may provide for intercomcapability with other sensors and/or security applications 108 (via thenetwork 102).

The client device(s) 106 (also referred to individually and collectivelyas 106) are computing devices having data processing and communicationcapabilities. In some embodiments, a client device 106 may include aprocessor (e.g., virtual, physical, etc.), a memory, a power source, anetwork interface, and/or other software and/or hardware components,such as a display, graphics processor, wireless transceivers, keyboard,camera, sensors, firmware, operating systems, drivers, various physicalconnection interfaces (e.g., USB, HDMI, etc.).

The client devices 106 may couple to and communicate with one anotherand the other entities of the environment 100 via the network 102 usinga wireless and/or wired connection. Examples of client devices 106 mayinclude, but are not limited to, mobile phones (e.g., feature phones,smart phones, etc.), tablets, smartwatches or other smart wearables,laptops, desktops, netbooks, server appliances, servers, virtualmachines, TVs, set-top boxes, media streaming devices, portable mediaplayers, navigation devices, personal digital assistants, etc. Inaddition, while a single client device 106 is depicted in FIG. 1, itshould be understood that any number of client devices 106 may beincluded.

The server 160 may include one or more computing devices having dataprocessing, storing, and communication capabilities. For example, theserver 160 may include one or more hardware servers, virtual servers,server arrays, storage devices and/or systems, etc., and/or may becentralized or distributed/cloud-based. In some embodiments, the server160 may include one or more virtual servers, which operate in a hostserver environment and access the physical hardware of the host serverincluding, for example, a processor, memory, storage, networkinterfaces, etc., via an abstraction layer (e.g., a virtual machinemanager).

While not depicted, the server 160 may include a (physical, virtual,etc.) processor, a non-transitory memory, a network interface, and adata store 168, which may be communicatively coupled by a communicationsbus. Similarly, the client device 106 may include a physical processor,a non-transitory memory, a network interface, a display, an inputdevice, a sensor, and a capture device. It should be understood that theserver and the client device may take other forms and include additionalor fewer components without departing from the scope of the presentdisclosure.

Software operating on the server 160 (e.g., the management engine 170,an operating system, device drivers, etc.) may cooperate and communicatevia a software communication mechanism implemented in association with aserver bus. The software communication mechanism can include and/orfacilitate, for example, inter-process communication, local function orprocedure calls, remote procedure calls, an object broker (e.g., CORBA),direct socket communication (e.g., TCP/IP sockets) among softwaremodules, UDP broadcasts and receipts, HTTP connections, etc. Further,any or all of the communication could be secure (e.g., SSH, HTTPS,etc.).

As shown, the server 160 may include a management engine 170 embodying aremotely accessible security service. The management engine 170 may senddata to and receive data from the other entities of the system includingthe security applications 108, a sensor management modules operable bythe processor 124, and a detection, capture, and processing modulesoperable by the processor 143. The management engine 170 may beconfigured to store and retrieve data from one or more informationsources, such as the data store 168. In addition, while a single server160 is depicted in FIG. 1, it should be understood that one or moreservers 160 may be included.

While not specifically shown, the server 160 may include a data storefor storing and providing access to data. The data store may store datareceived from other elements of the environment 100 include, forexample, a sensor management module executed by the processor 143, adetection, capture, and processing module executed by the processor 124,and/or instances of a security application 108 executable by the clientdevices 106, and may provide data access to these entities. Forinstance, the data store may store, among other data, images, motionimages, user settings, user account information, electronic addressinformation, security logs associated with security installations, anyinformation received from other entities of the system, access logs,etc.

In some embodiments, the security application 108, management engine170, security relay station(s) 120, etc., may require users to beregistered to access the acts and/or functionality provided by them. Forexample, to access various acts and/or functionality provided by thesecurity application 108, management engine 170, and/or security relaystation(s) 120, these components may require a user to authenticatehis/her identity (e.g., by confirming a valid electronic address). Insome instances, these entities 108, 120, 160, etc., may interact with afederated identity server (not shown) to register/authenticate users.Once registered, these entities 108, 120, 160, etc., may require a userseeking access to authenticate by inputting credentials in an associateduser interface.

In some embodiments, the management engine 170 may route the settings tothe relay station 120 associated with the sensor(s) 140. For example,the relay station 120 may receive the settings from the managementengine 170 via the network 102 using a suitable data transmissionprotocol, as discussed elsewhere herein, and the relay station 120 maystore the settings in the memory 126 and relay (e.g., push) the settingsto the appropriate sensors 140. In some instances, the settings may beapplicable to all the sensors 140 of the security installation and therelay station 120 may generate and send corresponding settingsinstructions to each of the sensors 140. In some instances, the settingsmay only be applicable to a subset (e.g., fewer than all) of the sensors140 of the security installation. In this case, the settings datareceived from the management engine 170 indicate which specific sensors140 the settings are applicable to, and the relay station 120 maygenerate and send settings instructions to the sensors 140 specified insettings data.

In some embodiments, each sensor 140 that received settings instructionsfrom the relay station 120 stores the settings data on a memory of themicrocontroller 145, such as the memory 144. The detection, capture, andprocessing module uses these settings instructions to control themonitoring being performed by the sensor 140. In some embodiments, thesettings instructions may be changes to existing parameters, thuseffecting the performance of the sensor 140 with respect to thoseparameters.

Example settings/parameters may include, but are not limited to: thesensitivity of PIR Sensor; the length of buffer after the PIR Sensordetects an event (the buffer reflects the amount of time a user has toreact before re-arming); a smoke detector setting enabling or disablingthe smoke detector of a sensor 140 (which can preserve battery life); aLED Flash flag setting, which can, for example, be set to on all thetime, off, scheduled on or off (e.g., day, time of day, etc.), on or offdepending on the mount of light detected by a photon detector, etc.; asiren setting, which, for example, can be set to turn on when the sensor140 is tripped, off all the time, delayed so when motion is detected itturns on after a certain specified, timeframe, etc. (the siren can alsobe activated on demand using the security application 108 or a hardwarebutton the sensor 140 or relay station 120); various camera settingsgoverning the operation of the camera 148 (additionally or alternativelyto the foregoing flash settings), such as brightness, contrast, imagesize or resolution, FPS, or any other applicable camera setting;settings governing the operation of the transceiver 152 (e.g., a radiofrequency transceiver), such as settings controlling the power level ofthe transceiver to fit the needs of the customer's installationenvironment, optimize battery life and signal strength, etc.

Additional acts, structure, and/or functionality of at least the clientdevices 106, the server 160, the security relay station(s) 120, thesecurity sensor(s) 140, and their constituent components are describedin further detail below.

It should be understood that the environment 100 illustrated in FIG. 1is representative of one possible system, and that a variety ofdifferent system environments and configurations are contemplated andare within the scope of the present disclosure. For instance, variousfunctionality may be moved from a server to a client, or between asecurity relay station 120 to a security sensor 140, or vice versa,etc., and some embodiments may include additional or fewer computingdevices, services, and/or networks, and may implement variousfunctionality on another device. Further, various entities of theenvironment 100 may be integrated into to a single computing device orsystem or additional computing devices or systems, etc. In furtherexamples, the environment 100 may include one or more third-partyservers (not shown) including an software application engines operableby the servers to provide various services such as social networking;email; blogging; micro-blogging; photo management; video, music andmultimedia hosting, distribution, and sharing; cloud-based data storageand sharing; a combination of one or more of the foregoing services; orany other service where users retrieve, collaborate, and/or shareinformation, which may be incorporated into the information beingpresented to the users via the security applications 108.

FIG. 9 is a flowchart of an example method 900 for provisioning alow-power processing device.

In block 902, the low-power processing device is powered on. In theexample depicted in FIG. 9, an instance of the security sensor 140 isreferenced. However, it should be understood that the method 900 isapplicable to other low-power processing devices having similaroperational requirements, such as power preservation and the ability tocommunicate wirelessly with other devices. This document encompassesthose devices as well.

In block 904, the processor 143 send the provisioning a request to therelay station 120 via the transceiver 152 using a wireless connectionand securely authenticates with the relay station 120. The securityrelay station 120 may using encryption (e.g., AES 128, 196, or 256, etc.encryption) to protect any data transmitted by it, such as thatexchanged with the sensor 140. In some embodiments, in the sensor 140 asignificant number of key data is preloaded into memory (e.g., 4 kB). Acopy of the key data may be stored in a data store of the server 160.When a corresponding relay station 120 interacts with a given sensor140, it can request and receive hashes of the key data from the server160, and use it to verify the identity of the sensor (e.g., that it isreally communicating with the right sensor) before pairing with it.

A security sensor 140 may periodically rotate its key data and thesecurity relay station/base station 120 can iterate through a set ofsequential keys to determine which one the security sensor 140 iscurrently using. Since, in some embodiments, the security relay station120 can determine the current date/time and a security sensor 140 maynot be able to, the security relay station 120 may send a requestrequesting the sensor 140 to rotate its key. In this way, the relaystation 120 may periodically update the encryption keys in case one iscompromised. However, it is noted that as data requirements of a givensecurity installation are low and relatively little data is transmittedwirelessly, it is unlikely that enough information can be collected tocrack the encryption protocol (e.g., around 20 million plain text andencrypted-text pairs may be required to crack the encryption).

In some embodiments, a security relay station 120 may have limitedaccess to the server 160 in the event a relay station 120 is physicallycompromised by an unauthorized user. If an unauthorized user obtainsphysical access to a user's system, users are notified of theirregularities (e.g., that the security installation may be down orcompromised). For instance, if there is period where the security sensor140 fails to sync with the relay station 120 for predetermined amount oftime, the server 160 (e.g., a management engine 170 thereof) will notifythe user that a sensor is down. The same may be true for a securityrelay station 120. The disruption could be due to jamming from amicrowave, failure in the sensor 140 or security relay station 120, orby malicious intent. The above security mechanisms provides a convenientway of protection for a variety of extreme cases.

In block 908, the processor 124 of the security relay station 120retrieves from the memory 126 state settings for the security sensor 140and provisions the security sensor 140 with the state settings in block910. The processor 145 of the security sensor 140 receives the statesettings for the security sensor 143 from the relay station 120, andconfigures, in block 912, the components of the security sensor 140using the state settings. In block 914, the method 900 places the sensorcomponents into an armed or disarmed sleep state as applicable.

White the method 900 is described in the context of powering on asecurity sensor 140, it is noted that the settings of the securitysensor 140, as well as the operation of the security sensor 120, can becontrolled remotely via the security application 108. Accordingly, whenthe security relay station 120 receives instructions from the server 160to update one or more operational parameters of the components of thesecurity sensor 140, such as the sensitivity of the motion sensor 150 n,activation or deactivation of the siren 155, activation or deactivationof the smoke sensor 150 a, etc., the security relay station 120provisions the instructions to the security sensor 140 responsive toreceiving a check-in signal from the security sensor 140 in a mannersubstantially similar to that described in FIG. 9. Similarly, when aremotely-initiated user instruction is received by the security relaystation 120 to capture a photograph or video using the camera 148,corresponding instructions are provided to the security sensor 140responsive to receiving a check-in signal from the security sensor 140,which the security sensor 140 then carries out.

The frequency at which the security sensor 140 checks and with thesecurity relay station 120 may be fixed or dynamic. In some embodiments,the system 100 may learn user patterns based on the monitoring beingperformed by the security sensor(s) 140 and/or the user input providedvia the security application 108, and may set the frequency in which thesecurity sensor 140 checks in with the security relay station 120 basedon the learned behavior. For example, the management engine 170 on theserver 160 may include machine-learning models, such as a Bayesiannetwork, decision tree, or other suitable machine learning models thatcan analyze the user pattern data stored in the data store of the server160 and output updated sleeping cycles for each of the sensors 140 of agiven installation. The following example inputs could be used for suchlearning, such as periods of inactivity, arm and disarm frequency andoccurrence, time of day, season, etc.

In some embodiments, where the security sensor 140 is trippedfrequently, the processor 143 may increase the check-in frequency toincrease performance and provide a more responsive experience to theuser. On the other hand, if the security sensor 140 is trippedinfrequently, the processor 143 may decrease the check-in frequency toavoid unnecessarily wasting power. For example, a default frequency mayinstruct the processor 143 to check-in with the security relay station120 every six seconds, but as the sensor becomes increasingly trippedbased activity that is detected within the monitored zone, the processor143 may increase the frequency to three seconds. As these periodiccheck-ins account for a considerable amount of the battery life of thesecurity sensor 140, due to the wireless transmission being performed bythe transceiver 152, dynamically adapting the check-in frequency toaccount for periods of inactivity is advantageous as it preventsunnecessary energy waste.

In some embodiments, the client devices 106 may transmit data to theother entities of the network 102 using security protocols (e.g., SSL(HTTPS) certificates) and the server 160 may exchange data with thesecurity relay station(s) 120 using two-way (or bi-directional) SSL(HTTPS) encryption and certificates (e.g., under the presumption thatneither node trusts the other).

FIG. 12A is a view of an example sensor 140 and FIG. 12B is a view of anexample relay station 120. FIG. 12A in particular depicts an examplesensor 140 having a body 1202 for housing the internal components of thesensor 140, which include a PIR sensor for detecting moving objectswithin its field of view, LED(s) 1204 for providing light/flash forcapturing images with camera and/or serving as visual indicators of thestatus of the sensor 140 (e.g., green indicating the sensor 140 isoperating correctly, red indicating a problem with the sensor 140,etc.), a camera 148 for capture images of detected moving objects, etc.The housing may include a shield for covering a window in the body andhaving an aperture through which the lens of the camera is directed. Thebody further includes a lid 1206 covering the topside of the sensor. Thelid is removable and depending on the embodiment includes a plurality ofholes through which fastening devices may be passed to either fasten thesensor to a mounting surface (e.g., the ceiling) or fasten the lid tothe main body of the sensor 140. In further embodiments, adhesive tapeor other fastening devices (e.g., magnets) may be used to fasten the lidto the mounting surface.

FIGS. 6A-6E depict example global variables that the microcontroller 145and the memory 144 may preserve during the sleep cycle of the processor143. The depicted code 600 is written in c, but it should be understoodthat other suitable languages are also applicable. The includedstructures can preserve all of the user state settings of theperipherals if necessary.

In the above description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofthe present disclosure. However, it should be understood that thetechnology described herein can be practiced without these specificdetails. Further, various systems, devices, and structures are shown inblock diagram form in order to avoid obscuring the description. Forinstance, various embodiments are described as having particularhardware, software, and user interfaces. However, the present disclosureapplies to any type of computing device that can receive data andcommands, and to any peripheral devices providing services.

In some instances, various embodiments may be presented herein in termsof algorithms and symbolic representations of operations on data bitswithin a computer memory. An algorithm is here, and generally, conceivedto be a self-consistent set of operations leading to a desired result.The operations are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout this disclosure, discussions utilizingterms including “processing,” “computing,” “calculating,” “determining,”“displaying,” or the like, refer to the action and processes of acomputer system, or similar electronic computing device, thatmanipulates and transforms data represented as physical (electronic)quantities within the computer system's registers and memories intoother data similarly represented as physical quantities within thecomputer system memories or registers or other such information storage,transmission or display devices.

Various embodiments described herein may relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, or it may comprise ageneral-purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program may bestored in a computer readable storage medium, including, but is notlimited to, any type of disk including floppy disks, optical disks,CD-ROMs, and magnetic disks, read-only memories (ROMs), random accessmemories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, flashmemories including USB keys with non-volatile memory or any type ofmedia suitable for storing electronic instructions, each coupled to acomputer system bus.

Various aspects of the technology described herein can take the form ofa hardware embodiment, a software embodiment, or embodiments containingboth hardware and software elements. For instance, the technology may beimplemented in software, which includes but is not limited to firmware,resident software, microcode, etc. Furthermore, the technology can takethe form of a computer program product accessible from a computer-usableor computer-readable medium providing program code for use by or inconnection with a computer or any instruction execution system. For thepurposes of this description, a computer-usable or computer readablemedium can be any non-transitory storage apparatus that can contain,store, communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.

A data processing system suitable for storing and/or executing programcode may include at least one processor coupled directly or indirectlyto memory elements through a system bus. The memory elements can includelocal memory employed during actual execution of the program code, bulkstorage, and cache memories that provide temporary storage of at leastsome program code in order to reduce the number of times code must beretrieved from bulk storage during execution. Input/output or I/Odevices (including but not limited to keyboards, displays, pointingdevices, etc.) can be coupled to the system either directly or throughintervening I/O controllers.

A computer network, such as the network 102 may include any number ofnetworks and/or network types. For example, the network 102 may include,but is not limited to, one or more local area networks (LANs), personalcommunication networks (PANs), such as Bluetooth®, IrDA™, Zigbee®, etc.,wide area networks (WANs) (e.g., the Internet), virtual private networks(VPNs), mobile (cellular) networks (e.g., a mobile network), wirelesswide area network (WWANs), WiMAX® networks, peer-to-peer networks, otherinterconnected data paths across which multiple devices may communicate,various combinations thereof, etc.

The private and public networks may have any number of configurationsand/or topologies. Data may be transmitted between these devices via thenetworks using a variety of different communication protocols including,for example, various Internet layer, transport layer, or applicationlayer protocols. For example, data may be transmitted via the networksusing transmission control protocol/Internet protocol (TCP/IP), userdatagram protocol (UDP), transmission control protocol (TCP), hypertexttransfer protocol (HTTP), secure hypertext transfer protocol (HTTPS),dynamic adaptive streaming over HTTP (DASH), real-time streamingprotocol (RTSP), real-time transport protocol (RTP) and the real-timetransport control protocol (RTCP), voice over Internet protocol (VOIP),file transfer protocol (FTP), WebSocket (WS), wireless access protocol(WAP), various messaging protocols (SMS, MMS, XMS, IMAP, SMTP, POP,WebDAV, etc.), or other known protocols.

The mobile network may include a cellular network having distributedradio networks and a hub. In some embodiments, the client devices 106may send and receive signals to and from a transmission node of themobile network over one or more of a control channel, a voice channel, adata channel, etc. In some embodiments, one or more client devices 106may connect to a wireless wide area network (WWAN) of the mobilenetwork. The mobile network and client devices 106 may use amultiplexing protocol or a combination of multiplexing protocols tocommunicate including, for example, FDMA, CDMA, SDMA, WDMA, or anyderivative protocols, or the like, etc. The mobile network of thenetwork 102 and client devices 106 may also employ multiple-input andoutput (MIMO) channels to increase the data throughput over the signallines coupling the mobile network and client devices 106. The mobilenetwork may be any generation mobile phone network. In some instances,the mobile network 102 maybe a 2G or 2.5G GSM, IS-95, etc., network; a3G UTMS, IS-2000, etc., network; a 4G HSPA+, 3GPP LTE, WiMax™, 5G (andbeyond) network; etc. In some instances, the mobile network may includea backwards-compatible multi-generational network that supports two ormore technology standards.

Data transmitted by the network 102 may include packetized data (e.g.,Internet Protocol (IP) data packets) that is routed to designatedcomputing devices coupled to the network 102. In some embodiments, thenetwork 102 may include a combination of wired and wireless networkingsoftware and/or hardware that interconnects the computing devices of thesystem (e.g., environment 100). For example, the network 102 may includepacket-switching devices that route the data packets to the variouscomputing devices based on information included in a header of the datapackets.

The network adapters described herein may also be coupled to the systemto enable the data processing system to become coupled to other dataprocessing systems, storage devices, remote printers, etc., throughintervening private and/or public networks.

Finally, the structure, algorithms, and/or interfaces presented hereinare not inherently related to any particular computer or otherapparatus. Various general-purpose systems may be used with programs inaccordance with the teachings herein, or it may prove convenient toconstruct more specialized apparatus to perform the required methodblocks. The required structure for a variety of these systems willappear from the description above. In addition, the specification is notdescribed with reference to any particular programming language. It willbe appreciated that a variety of programming languages may be used toimplement the teachings of the specification as described herein.

The foregoing description has been presented for the purposes ofillustration and description. It is not intended to be exhaustive or tolimit the specification to the precise form disclosed. Manymodifications and variations are possible in light of the aboveteaching. It is intended that the scope of the disclosure be limited notby this detailed description, but rather by the claims of thisapplication. As will be understood by those familiar with the art, thespecification may be embodied in other specific forms without departingfrom the spirit or essential characteristics thereof. Likewise, theparticular naming and division of the modules, routines, features,attributes, methodologies and other aspects are not mandatory orsignificant, and the mechanisms that implement the specification or itsfeatures may have different names, divisions and/or formats.

Furthermore, the modules, routines, features, attributes, methodologiesand other aspects of the disclosure can be implemented as software,hardware, firmware, or any combination of the foregoing. Also, wherevera component, an example of which is a module, of the specification isimplemented as software, the component can be implemented as astandalone program, as part of a larger program, as a plurality ofseparate programs, as a statically or dynamically linked library, as akernel loadable module, as a device driver, and/or in every and anyother way known now or in the future. Additionally, the disclosure is inno way limited to implementation in any specific programming language,or for any specific operating system or environment.

What is claimed is:
 1. A security sensor comprising: a battery powersupply; a camera coupled to the battery power supply to receive power,the camera being placed in a camera sleep state and being wakeable to acamera awake state; an activity sensor coupled to the battery powersupply to receive the power, the activity sensor configured to detectactivity within a zone proximate the security sensor; a processor placedin a processor sleep state and wakeable to a processor awake state, theprocessor coupled to the battery power supply to receive power, andcoupled to the camera to receive image data including images of theactivity within the zone; and a microcontroller coupled to the batterypower supply to receive the power, coupled to the activity sensor toreceive interrupts responsive to detection by the activity sensor of theactivity within the zone proximate the security sensor, and coupled to aprocessor to send and receive data, and, responsive to receiving a firstinterrupt from the activity sensor, the microcontroller being configuredto place the processor in an awake state and place the camera in anawake state, wherein the camera, responsive to being placed in thecamera awake state, captures a set of images of the activity within thezone and provides image data including the set of images to theprocessor, responsive to the image data being provided to the processor,the camera is placed in the camera sleep state, and responsive to theimage data being transmitted to a remote network entity, the processoris placed in the processor sleep state.
 2. The security sensor of claim1, wherein the processor, upon being placed in the processor awakestate, polls the microcontroller for any events that occurred during theprocessor sleep state, determines a motion detection event occurred,places the camera in the camera awake state, sends a capture signal tothe camera, and receives and processes the image data including the setof images.
 3. The security sensor of claim 1, further comprising: anon-transitory memory coupled to the battery power supply and theprocessor; and a transceiver coupled to the battery power supply, thememory, and the processor, wherein, responsive to receiving the imagedata from the camera, the processor caches the image data in thenon-transitory memory and the transceiver retrieves the image datacached in the non-transitory memory and transmits the image data to theremote security sensor relay for transmission to a security serveraccessible via the Internet.
 4. The security sensor of claim 3, whereinthe battery power supply, the camera when idle, the activity sensor whenidle, the microcontroller, the processor when in the processor sleepstate, the non-transitory memory, and the transceiver when idle,collectively draw a current of less than or equal to about 100 microamps.
 5. The security sensor of claim 1, further comprising: anon-transitory memory integrated with the microcontroller that storesstate data including operational settings for the activity sensor,wherein upon awaking the processor retrieves the state data from thenon-transitory memory integrated with the microcontroller.
 6. Thesecurity sensor of claim 1, wherein the processor operates on a sleepcycle and includes a sleep timer that routinely wakes the processor fromthe processor sleep state based on an expiration of a sleeping period.7. The security sensor of claim 6, wherein the sleeping period ispredetermined or dynamically set.
 8. The security sensor of claim 1,wherein the activity sensor is a motion sensor configured to detectmotion of a moving object within the zone.
 9. The security sensor ofclaim 8, wherein the motion sensor is a passive infrared sensor.
 10. Thesecurity sensor of claim 1, wherein the activity sensor is a smokedetector configured to detect smoke within the zone.
 11. A method forcontrolling operation of a security sensor, comprising: placing aprocessor of the security sensor in a processor sleep state, theprocessor being wakeable to an awake state and being coupled to a cameraconfigured to capture a zone of a premises proximate the securitysensor; detecting with an activity sensor activity occurring within thezone; receiving at a microcontroller a first interrupt from the activitysensor responsive to detection by the activity sensor of the activitywithin the zone proximate the security sensor; responsive to receivingat the microcontroller the first interrupt from the activity sensor,placing the processor in the processor awake state; signaling the camerato automatically capture a set of images; receiving the image dataincluding the set of images captured by the camera; and automaticallyplacing the processor back into the processor sleep state responsive toa transmission of the set of images via a computer network.
 12. Themethod of claim 11, further comprising: upon placing the processor inthe awake state, polling, with the processor via a communications bus,the microcontroller for any events that occurred during the sleep state;determining a motion detection event occurred; and receiving the imagedata including the set of images at the processor from the camera andprocessing the image data.
 13. The method of claim 11, furthercomprising: responsive to the processor receiving the image data fromthe camera, caching the image data in a non-transitory memory;retrieving using a transceiver the image data cached in thenon-transitory memory; and transmitting the image data to a remotesecurity sensor relay for transmission to a security server accessiblevia the Internet.
 14. The method of claim 13, wherein a battery powersupply, the camera when idle, the activity sensor when monitoring, themicrocontroller, the processor when in the processor sleep state, thenon-transitory memory, and the transceiver when idle, collectively drawa current of less than or equal to 50 micro amps.
 15. The method ofclaim 11, further comprising: storing state data in a non-transitorymemory integrated with the microcontroller; and upon placing theprocessor in the awake state, retrieving using the processor the statedata from the non-transitory memory integrated with the microcontroller.16. The method of claim 11, further comprising: operating the processoron a sleep cycle; and routinely waking the processor from the sleepstate using a sleep timer based on an expiration of a sleeping period.17. The method of claim 16, wherein the sleeping period is predeterminedor dynamically set.
 18. The method of claim 11, wherein the activitysensor is a motion sensor configured to detect motion of a moving objectwithin the zone.
 19. The method of claim 18, wherein the motion sensoris a passive infrared sensor.
 20. A method comprising: placing an imagesensor of a security sensor in an inactive state, the image sensorpositioned to capture images of a zone proximate the security sensor;receiving a user-initiated interrupt or an activity-sensor-initiatedinterrupt from a microcontroller at the image sensor; responsive toreceiving the user-initiated interrupt or the activity-sensor-initiatedinterrupt, placing a processor of the security sensor in a processorawake state; automatically capturing using the image sensor a set ofimage frames of a potential threat within the zone proximate to thesecurity sensor; sending images including the set of image frames to theprocessor while in the processor awake state; transmitting using awireless transceiver the image data via a wireless connection to aremote security relay station; and automatically placing the processorinto a processor sleep state responsive to transmitting the image data.21. The method of claim 20, further comprising: sensing using a lightsensor to determine available light within the zone; determining that aflash was not triggered during capture of the set of image frames basedon the available light; and triggering the flash to alert potentialthreat in the zone that the set of images frames were captured.
 22. Themethod of claim 20, further comprising: retrieving image sensor settingsfrom the microcontroller; and configuring the image sensor using theimage sensor settings.